Did a careful review against the c2sp.org/tlog-mirror spec and ran the pre-push checks. Wire-format math, ticket scheme, and test coverage are solid. A few things to address before this lands:

Must-fix

1. Stale TicketSealer references break cargo doc (error.rs, wire.rs)

Three intra-doc links to crate::TicketSealer survive from an earlier AEAD-based design — the type is now TicketMacer. Confirmed locally:

$ RUSTDOCFLAGS=\"-D rustdoc::broken_intra_doc_links\" cargo doc -p tlog_mirror --no-deps
error: unresolved link to \`crate::TicketSealer\`
  --> crates/tlog_mirror/src/wire.rs:64:26
error: unresolved link to \`crate::TicketSealer\`
  --> crates/tlog_mirror/src/error.rs:62:41

Locations:

• crates/tlog_mirror/src/wire.rs:64 — ``TicketSealer``
• crates/tlog_mirror/src/error.rs:62 — `Errors returned by `TicketSealer`.`

While you're in error.rs, the TicketError variant docs are also AEAD-flavored leftovers that no longer match the implementation:

• Line 65: "sealed ticket too short: ... 12-byte nonce" — there is no nonce; the threshold is TAG_LEN = 16.
• Line 70: "AEAD authentication failed: either the ciphertext or the nonce has been tampered with" — no AEAD, no nonce, no ciphertext.

Suggest rewording to refer to TicketMacer, TAG_LEN, and HMAC tag verification.

2. cargo package -p tlog_mirror fails — missing README.md

crates/tlog_mirror/Cargo.toml:3 hard-codes readme = \"README.md\", but no README.md exists in the crate directory. Sibling crates (tlog_witness, tlog_cosignature, static_ct_api) use readme.workspace = true, which resolves to the workspace root README during packaging.

$ cargo package -p tlog_mirror --no-verify --allow-dirty --list
error: readme \`README.md\` does not appear to exist (relative to \`.../crates/tlog_mirror\`).

This will also block any future cargo publish. Easiest fix: change to readme.workspace = true, matching siblings.

3. Integer overflow in package_ranges iterator (wire.rs:185)

let next_boundary = (start / PACKAGE_ALIGNMENT + 1) * PACKAGE_ALIGNMENT;

This overflows u64 whenever start / 256 == u64::MAX / 256, i.e. roughly start >= 0xFFFF_FFFF_FFFF_FF00. In debug builds this panics with attempt to multiply with overflow; in release it wraps to 0, which makes end = next_boundary.min(upload_end) = 0, and since self.next = end = 0, the iterator silently restarts and yields wrong ranges.

Reachable from network input because AddEntriesRequestHeader::read_from accepts any upload_end up to u64::MAX. No real log will ever hit 2^64 entries, but a malicious or buggy peer absolutely can put any 8-byte value on the wire.

Suggested fix — saturate at upload_end:

let next_boundary = (start / PACKAGE_ALIGNMENT)
    .checked_add(1)
    .and_then(|q| q.checked_mul(PACKAGE_ALIGNMENT))
    .unwrap_or(self.upload_end);
let end = next_boundary.min(self.upload_end);

Add a regression test, e.g. package_ranges(u64::MAX - 1, u64::MAX) should yield (u64::MAX - 1, u64::MAX) and then terminate.

Should-fix

4. PR description claims publish = false but the manifest doesn't have it

The PR description says the crate is publish = false while the spec stabilizes, but crates/tlog_mirror/Cargo.toml has only [package.metadata.release] release = false — that's a cargo-release automation marker, not a cargo publish gate. (static_ct_api, which is explicitly published per AGENTS.md, has the same metadata.release block.) Either add publish = false under [package] or amend the PR description so it doesn't promise a guard that isn't there. Worth being explicit since the AGENTS.md "crates.io" boundary is an approval gate.

Nits / discussion

5. parse_decimal_u64 is stricter than the spec text

The spec says "in decimal" without explicitly forbidding leading zeros / + / whitespace. The current parser rejects all of those, which is fine for serializing — we only want one canonical form — but slightly aggressive when parsing a body produced by another mirror implementation. The inline comment already justifies this ("we want a single canonical encoding for each integer"), so I'm fine leaving it as-is, but worth flagging in case there's appetite for a Postel split (lenient parser, strict serializer).

6. Test gap (low priority)

EntryPackage::read_from converts num_entries: u64 to usize and only fails on 32-bit targets. Not realistically reachable from a tlog mirror, but a #[cfg(target_pointer_width = \"32\")] test is essentially free if you want to lock the behavior in.

Pre-push checks I ran locally on the head commit:

• cargo clippy --workspace --all-targets -- -Dwarnings -Dclippy::pedantic ✅
• cargo test -p tlog_mirror ✅ (34/34)
• cargo fmt --all --check ✅
• cargo doc -p tlog_mirror ❌ (broken intra-doc links — see #1)
• cargo package -p tlog_mirror --no-verify --list ❌ (missing README — see #2)

Re-reviewed against the previous review's findings and against the spec. All three must-fix items and the should-fix item are addressed; pre-push checks (including the two that previously failed) all pass locally on the head commit.

Previous review items — verified fixed

1. Stale TicketSealer references / AEAD verbiage ✅

• wire.rs:64 now points to crate::TicketMacer.
• error.rs:62 rewords to [\TicketMacer`](crate::TicketMacer)`.
• error.rs:65–75 rewords the variants to refer to TAG_LEN (16 bytes) and HMAC tag verification — no more "12-byte nonce" / "AEAD authentication failed".
• RUSTDOCFLAGS="-D rustdoc::broken_intra_doc_links" cargo doc -p tlog_mirror --no-deps now passes.

The only remaining mention of "AEAD" in the crate is in ticket.rs:34, in the doc paragraph that explicitly invites operators to roll their own AEAD-based scheme — that's intentional, not a leftover.

2. Missing README breaks cargo package ✅

• crates/tlog_mirror/Cargo.toml:10 now uses readme.workspace = true, matching siblings.
• cargo package -p tlog_mirror --no-verify --allow-dirty --list succeeds and includes README.md (resolved from the workspace root).

3. Integer overflow in package_ranges ✅

• wire.rs:189–192 now uses checked_add(1).and_then(|q| q.checked_mul(PACKAGE_ALIGNMENT)).unwrap_or(self.upload_end), with an inline comment explaining the saturation.
• New regression test package_ranges_no_overflow_at_u64_max (wire.rs:540–553) covers both u64::MAX - 1, u64::MAX and edge, u64::MAX (where edge = u64::MAX - (u64::MAX % 256)). Both yield a single correct range and terminate.
• Total tests: 35 (up from 34).

4. publish = false not in manifest ✅

• crates/tlog_mirror/Cargo.toml:5 now sets publish = false with a comment explaining it'll be lifted once the spec stabilizes. [package.metadata.release] release = false is also retained for cargo-release.

Pre-push checks (head commit 789acbb)

cargo clippy --workspace --all-targets -- -Dwarnings -Dclippy::pedantic   ✅
cargo test                                                                ✅ (full workspace green; tlog_mirror 35/35)
cargo fmt --all --check                                                   ✅
RUSTDOCFLAGS="-D rustdoc::broken_intra_doc_links" cargo doc -p tlog_mirror --no-deps  ✅
cargo package -p tlog_mirror --no-verify --allow-dirty --list             ✅

(cargo machete not installed in this sandbox; CI runs it.)

Tiny nit (non-blocking)

The PR body still says "34 unit tests covering …". With the overflow regression test added, it's 35. Worth a one-character tweak before merge if you're amending the description; otherwise no action needed.

LGTM — approving.